|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Informational RFC approved January 2006. Obsoleted by RFC 4330.
|
|
3.
|
Justification for the specific reference:
|
|
|
Although Informational and obsoleted by RFC 5905 (2010), ITU-T H.810 uses the specs in this RFC as the mechanism to synchronize time and coordinate time distribution in a large, diverse Internet operating at rates from mundane to light-wave over its WAN Interface. This document describes the Simple Network Time Protocol (SNTP) Version 4, which is an adaptation of the Network Time Protocol (NTP) also utilized by Continua to synchronize computer clocks in the Internet. SNTP can be used when the ultimate performance of the full NTP implementation described in RFC 1305 is not needed or justified. ITU-T H.810 allows SNTP as a secondary means for synchronizing computer clocks used within the Continua architecture.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=4330
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Informational RFC approved October 1996. Obsoleted by RFC 4330. Obsoletes RFC 2030, RFC 1769. Errata exist.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
See 5. above.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Obsoletes: RFC 2030, 1769. Obsoleted by RFC 4330.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
None
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
